PR Summary

This pull request includes updates to the Azure SDK version, enhancements to logging and debugging, and improvements to error handling for Azure access token retrieval. The most important changes are grouped below by theme.

Dependency Updates:

• Updated Azure SDK dependency Azure.Identity from version 1.11.4 to 1.14.0 in Microsoft.PowerShell.PSResourceGet.csproj.
• Updated the .NET SDK version in global.json from 8.0.406 to 8.0.411.

Logging and Debugging Enhancements:

• Added debug logging to indicate whether a repository is unauthenticated in GetContainerRegistryAccessToken.
• Added debug logging when retrieving an anonymous access token from a realm in IsContainerRegistryUnauthenticated.

Error Handling Improvements:

• Modified GetAzAccessToken to accept a PSCmdlet parameter for logging warnings and implemented a timeout mechanism with CancellationTokenSource to prevent indefinite waits. Added specific error handling for timeout and general exceptions. [1] [2]

Configuration Updates:

• Added a pwsh parameter set to true in .ci/test.yml to enable PowerShell Core in CI tests.

Code Simplification:

• Removed redundant debug logging from ProcessResourceNameParameterSet in FindPSResource.cs.

PR Context

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • Documentation needed
    • Issue filed:
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    • Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
  • OR
  • I have considered the user experience from a tooling perspective and enumerated concerns in the summary.